Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Notes/Domino 8 Forum

Notes/Domino 8 Forum

Previous Next

Major bug: reproducible failure to send to some domains

I know this has been reported for some time, on several versions of Domino, and still it occurs.

I have some info that should lead to a resolution, but it is not rocket science.

It seems that when we get this error it is always that the Router task is reporting that it cannot send email to the host which is the DOMAIN. eg ACME.COM instead of MAIL.ACME.COM
These domains all have one thing in common: there is a DNS entry present which resolves the name of the domain to a different server from the mail server.
Consider this example:
www.acme.com resolves to 111.111.111.111
acme.com resolves to 111.111.111.111
mail.acme.com resolves to 222.222.222.222 as an MX record

(This is done so that people using browsers do not need to put in the "www")

What the Domino Router task seems to be doing is to use the name of the host instead of the correct MX record. It does this randomly, and will not re-query the DNS until a router restart.

here are the log entries:
...
01/07/2008 12:00:12 AM Router: No messages transferred to EXPERIENT-INC.COM (host EXPERIENT-INC.COM) via SMTP: The server is not responding
...restart the router...
01/07/2008 12:00:40 AM Router: [00000007] Transferring mail to domain EXPERIENT-INC.COM (host mail.global.sprint.COM [216.32.181.22]) via SMTP

Note how the entry in brackets is dramatically different - different machines. Hardly surprising that the mail banks up when it is not trying to go to the correct host.

If you want more details, pls email me: jcantor@netforce.com.au as I am very keen to get this fixed.


Feedback response number WEBB7QU3W8 created by ~Vera Quetponesterikle on 04/06/2009

Hi Priority message stuck in router... (~Kirk Pretoolit... 6.Dec.07)
. . Could more information be collected... (~Arnold Brerely... 6.Dec.07)
. . . . I will turn those on tonight (~Kirk Pretoolit... 7.Dec.07)
. . . . . . Results. I know, late but still (~Kirk Pretoolit... 7.Jan.08)
. . . . . . . . Additional results (~Kirk Pretoolit... 7.Jan.08)
. . . . . . . . . . Problem solved for now. (~Kirk Pretoolit... 14.Jan.08)
. . . . Major bug: reproducible failure to ... (~Vera Quetpones... 6.Apr.09)
. . . . . . re: Major bug: reproducible failure... (~Sarah Cistooma... 6.Apr.09)
. . . . . . . . ...or we could get Notes developmen... (~Vera Quetpones... 6.Apr.09)
. . . . . . . . . . re: Major bug: reproducible failure... (~Sarah Cistooma... 6.Apr.09)
. . . . . . . . . . solution? cause seems to be a DNS p... (~Vera Quetpones... 27.Apr.09)
. . . . . . . . . . . . Hotfix available (~Sigmund Dworel... 7.Jul.09)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS